Feedback-Aware Requirements Documents for Smart Devices

[Context/ Motivation] A smart device is a software-intensive system, which operates autonomously and interacts to some degree with other systems over wireless connections (e.g., a iRobot Roomba vacuum cleaner). These systems are often faced with uncertainty in the environment. Runtime representations of requirements have recently gained more interested to deal with this challenge and the term requirements at runtime was coined. These representations allow to reason about the requirements at runtime and to adapt the configuration of a system according to changes in the environment. [Questions/Problems] The research question is how the results of online monitoring of requirements and the system’s decisions about changes in the configuration are communicated to the requirements engineer to better understand the environment. There is a gap between the written requirements document and the dynamic requirements model inside the system. This problem is exacerbated by the fact that a requirements document are mostly informal while the dynamic requirements model is formal. [Principal ideas/results] This paper introduces an approach to bridge the gap between development time and runtime representations in order to keep them consistent and to facilitate a better understanding. We suggest to weave the feedback from the runtime system into requirements documents using a domainspecific language which keeps the informal nature of requirements. An annotated requirements document helps get a better understanding of the system’s actual behavior in a given environment. The approach is implemented using mbeddr, a novel domain-specific language for developing embedded systems, and illustrated in a case study.